home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
maximus
/
stbar20.zip
/
CUSTOM.DOC
< prev
next >
Wrap
Text File
|
1996-04-12
|
6KB
|
163 lines
Customizing StarBar V2.0
-----------------------------------------------------------------------------
Colours:
--------
There are two ways to change colours used within StarBar.
1) Use raw colour codes within StarBar.MH
2) Use colour defines in the StarBar.LH file.
Method 1:
This is pretty much explained in the StarBar.MH file, but I will
go over it here also.
In StarBar.MH, we have #define Statements which look like this:
#define ST_COL_DESC "\x16\x01\x03"
^^^^^^^^^^^^
This is the raw HEX colour
code for CYAN.
So, this statement tells StarBar it should print the file
description in CYAN.
Suppose we wanted to print it in BROWN? First, we need to know
the raw HEX code for BROWN. Have a look in COLOURS.TXT. On line
7 of that file we see that the colour code for BROWN is
\x16\x01\x06.
You will notice that the \x16\x01 part of the colour code appears
in all the colour codes. So, all we have to do is replace the
\x03 above with \x06
#define ST_COL_DESC "\x16\x01\x06"
Now our descriptions will be printed in BROWN.
You can change any of the #defines in StarBar.MH which contain
colour codes to anything found in COLOURS.TXT.
When changing any #defines in StarBar.MH, take notice of any spaces
(within the quotes), as they are there for a reason.
Method 2:
Colours for most of the strings used by StarBar are in the
StarBar.LH language file. In this file, you can use the colour
word to define the colour.
EG:
st_no_access= LRED "Sorry, you don't have access to this function!\n\n";
^^^^
Prints the access string in LightRed.
One side-note. Make sure you leave any control chars encountered as
they are. (the "\n\n" above is a good example. More on this below)
Also, I recommend sticking to the first 16 colour words listed in
COLOURS.TXT.
Language Files:
---------------
StarBar is capable of using multiple language files. Once you have your
primary language file using StarBar.LH, you can copy this file to another
name and include it in other language files.
However, if you don't have translated StarBar language files, I recommend
including StarBar.LH in all your "user heaps" in all the language files
you run.
If you have translated StarBar language files, include the file in the
appropriate language files.
For instance, say you have a French language file for StarBar called
STARFR.LH. Put it in your ..\m dir and include this filename in your
french language "user heap". (Same method as described in STARBAR.DOC)
MAID the French language file, and try it out. Run StarBar under French
and have a look.
Translating:
------------
Translating the StarBar.LH file shouldn't prove to be too difficult, but
there are a few things you should keep in mind:
- Some strings should be kept close or at the same length. Especially
the st_com_* strings as they are used in the command line which appears
at the bottom of the StarBar screen. If they are too long, they will
bleed onto the next line and will mess up the lightbar positioning
for the remote user.
- Take care to preserve the control characters (EG: "\n\n") These are
line feed characters and may have undesired effects on other strings
if omitted.
- Make sure you don't touch the =starbar statement which appears
after the version #define.
- Enclose all text in quotes (not the colour words)
- End each string with a ;
Help Files:
-----------
StarBar will make use of additional help files if they are available. The
default help file is SBHELP0.BBS. The "0" indicates this is a help file for
language #1. Language #2 would use SBHELP1.BBS. If a help file doesn't
exist for a particular language, SBHELP0.BBS will be displayed by default.
If your French language file is #4 in your change language menu, then
SBHELP3.BBS will be displayed.
Translating:
------------
Simply copy SBHELP0.MEC to the appropriate language number and edit all
the text. For French being Language #4, copy SBHELP0.MEC to SBHELP3.MEC,
edit the text then MECCA SBHELP3.MEC.
Keep in mind, if you change any hotkeys (explained below) you will have
to change the help files to reflect the change. EG: if you change X)Exit to
Q)uit, you will have to make the change in the help file, or your users
may become confused. (doesn't take much I know...<G>)
HotKeys:
--------
You can change some of the hotkey definitions in the STARBAR.MH file.
Just change the KEY_* as described in STARBAR.MH. Most hotkeys cannot
be changed (there shouldn't be a reason to change the KEY_DOWN #define,
for instance).
EG: To change [X]Exit to [Q]Quit we would do this:
- In STARBAR.MH, change:
#define KEY_EXIT "Xx"
to
#define KEY_EXIT "Qq" <-- You need both upper and lowercase!
- In STARBAR.LH, change
st_com_exit= GREEN "Exit ";
to
st_com_exit= GREEN "Quit "; <-- Take note of the space needed!
- In SBHELP#.MEC, change the lines which refer to "X" being needed to o
exit the program to "Q".
- Now, you will have to MAID <language>.mad , MEX STARBAR , and MECCA
SBHELP#.MEC to process the changes.
StarBar will now use "Q" to quit the program and the change will be noted
on the command footer.
-----------------------------------------------------------------------------
Basically, just play with StarBar until you get it working and looking
the way you want.
If you have any problems, feel free to send me mail, and I will get a
response to you with a solution.
See REGISTER.DOC for addresses...